Cross-device task registration and resumption

ABSTRACT

Systems and methods are disclosed for cross-device task registration and resumption. In one implementation, a task can be received from a task registration service of a first device associated with a user. Such a task can include an application identifier that identifies an application that executes on the device. A notification that the user has accessed a second device can be received. In response to the notification, the task can be provided to a task resumption service of the second device.

TECHNICAL FIELD

Aspects and implementations of the present disclosure relate to dataprocessing and, more specifically, but without limitation, tocross-device task registration and resumption.

BACKGROUND

With the increased availability of electronic devices such assmartphones, tablets, computers, etc., a single user can utilize severaldevices. Many of these devices include the same or similar capabilitiesand certain applications (e.g., media player applications, web browsers)are available for many different devices.

SUMMARY

The following presents a shortened summary of various aspects of thisdisclosure in order to provide a basic understanding of such aspects.This summary is not an extensive overview of all contemplated aspects,and is intended to neither identify key or critical elements nordelineate the scope of such aspects. Its purpose is to present someconcepts of this disclosure in a compact form as a prelude to the moredetailed description that is presented later.

In one aspect of the present disclosure, a task is received from a taskregistration service of a first device associated with a user. Such atask can include an application identifier that identifies anapplication that executes on the device. A notification that the userhas accessed a second device is received. In response to thenotification, the task is provided to a task resumption service of thesecond device.

In another aspect, a task is registered at a first device associatedwith a user. Such a task can include an application identifier thatidentifies an application that executes on the first device, an actionassociated with the application as executed on the first device, acontent item associated with the application as executed on the firstdevice, and an operation state associated with the application asexecuted on the first device. Such a task is provided to a taskmanagement service.

In yet another aspect, a task is received at a first device associatedwith a user. Such a task can include an application identifier thatidentifies an application that executed on a second device associatedwith the user, an action associated with the application as executed onthe second device, a content item associated with the application asexecuted on the second device, and an operation state associated withthe application as executed on the second device. Such a task can beresumed at the first device.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects and implementations of the present disclosure will be understoodmore fully from the detailed description given below and from theaccompanying drawings of various aspects and implementations of thedisclosure, which, however, should not be taken to limit the disclosureto the specific aspects or implementations, but are for explanation andunderstanding only.

FIG. 1 illustrates an example system, in accordance with an exampleembodiment.

FIG. 2 illustrates one example scenario described herein, according toan example embodiment.

FIG. 3 is a flow chart illustrating a method, in accordance with anexample embodiment, for cross-device task registration and resumption.

FIG. 4 is a flow chart illustrating another method, in accordance withan example embodiment, for cross-device task registration andresumption.

FIG. 5 is a flow chart illustrating yet another method, in accordancewith an example embodiment, for cross-device task registration andresumption.

FIG. 6 is a block diagram illustrating components of a machine able toread instructions from a machine-readable medium and perform any of themethodologies discussed herein, according to an example embodiment.

DETAILED DESCRIPTION

Aspects and implementations of the present disclosure are directed tocross-device task registration and resumption.

It can be appreciated that a single user can utilize multiple devices(e.g., a smartphone, tablet device, personal computer). For example, itcan be more convenient for a user to utilize a portable device (e.g., asmartphone) while traveling and a non-mobile device (e.g., a personalcomputer (PC)) while stationary. Additionally, a user can have apreference for one device (when available) over another. Accordingly,even when a user is utilizing one device (e.g. a smartphone), in certainscenarios (e.g., when the user arrives at his/her office) it can beadvantageous for the user to transition to another device (e.g., a PC).In such a scenario, the user's first device can be running variousapplications (e.g., a media player application that is playing a song,video). Though the user can wish to resume such application(s) at thesecond device (e.g., the PC) to which he/she is transitioning to,existing technologies do not enable or provide a framework for such taskresumption. Instead, the user is left to manually resume eachapplication at the second device. Additionally, existing technologies donot provide a framework that enables a user to manage multiple tasks(each of which may correspond to a different application) and to resumesuch task(s) (e.g., at a different device).

Accordingly, described herein in various implementations aretechnologies, including methods, machine readable mediums, and systems,that enable tasks to be captured/registered at a first device. Thereferenced tasks can reflect various aspects of the application(s) asthey are running on a user's first device (e.g., what operation(s) anapplication is currently performing). Upon registering such task(s) at afirst device, the task(s) can be provided to and stored in a centraltask store. Upon determining that the user has transitioned to a seconddevice, the stored task(s) can be provided to such a device and resumedthere. In doing so, a common platform can be provided through whichtask(s) associated with multiple applications can be registered (e.g.,at one device) and subsequently resumed at other device(s).

Additionally, in certain implementations the referenced task resumptionframework can be implemented in conjunction with a personal assistantapplication or service. Such a personal assistant can provide aninterface (e.g., a visual and/or audio communication interface) throughwhich a user can request and/or receive information, content, etc.(e.g., contextually relevant content). The personal assistant can alsoenable a user to initiate and/or configure various aspects ofapplications running on a device. Accordingly, as described herein, thepersonal assistant can provide a common/central interface through whicha user can manage various tasks. For example, the personal assistant canenable a user to provide input/approval at one device with respect towhether or not to register a particular task. By way of further example,the personal assistant can notify a user at another device of variousstored task(s) that can be resumed. In doing so, the personal assistantprovides a common interface through which a user can manage and resumemultiple tasks which pertain to multiple applications.

It can therefore be appreciated that the described technologies aredirected to and address specific technical challenges and longstandingdeficiencies in multiple technical areas, including but not limited toapplication management, device management, and personal assistantcommunication interfaces. As described in detail herein, the disclosedtechnologies provide specific, technical solutions to the referencedtechnical challenges and unmet needs in the referenced technical fieldsand provide numerous advantages and improvements upon conventionalapproaches. Additionally, in various implementations one or more of thehardware elements, components, etc., referenced herein operate toenable, improve, and/or enhance the described technologies, such as in amanner described herein.

FIG. 1 illustrates an example system 100, in accordance with someimplementations. As shown, the system 100 includes various devices suchas device 110A and device 110B (collectively device(s) 110). Each device110 can be a laptop computer, a desktop computer, a terminal, a mobilephone, a tablet computer, a smart watch, a personal digital assistant(PDA), a digital music player, a server, and the like. User 130 can he ahuman user who interacts with device(s) 110. For example, user 130 canprovide various inputs (e.g., via an input device/interface such as akeyboard, mouse, touchscreen, etc.) to device(s) 110A. Device(s) 110 canalso display, project, and/or otherwise provide content to user 130(e.g., via output components such as a screen, speaker, etc.). Asdescribed herein, user 130 can interact with one device (e.g., device110A) at one time and later interact with another device (e.g., device110B).

As shown in FIG. 1, device 110A can include various applications such asapplication 118A and application 118B (collectively, application(s)118). Each application 118 can be stored in memory of device 110 (e.g.memory 630 as depicted in FIG. 6 and described below). One or moreprocessor(s) of device 110 (e.g., processors 610 as depicted in FIG. 6and described below) can execute such application(s). In doing so,device 110 can be configured to perform various operations, presentcontent to user 130, etc. Examples of application(s) 118 include but arenot limited to: web browsers, media players, social media/messagingapplications, content creation applications, mobile ‘apps,’ etc.

As shown in FIG. 1, device 110A can also include task registrationservice 112, security engine 114, and personal assistant engine 116.Each of task registration service 112, security engine 114, and personalassistant engine 116 can be, for example, an application or modulestored on device 110A (e.g., in memory of device 110A). When executed(e.g., by processor(s) of device 110A), such service(s)/engine(s)configure or otherwise enable device 110A to perform various operationssuch as are described herein.

For example, task registration service 112 can configure or enabledevice 110A to capture or register various task(s) associated with anapplication 118 executing on device 110A. Each of the referenced task(s)can be, for example, a record that reflects various aspects of theexecution of the application at the device. Further aspects of thereferenced task(s) are described in detail below.

As also shown in FIG. 1, in certain scenarios user 130 can utilize otherdevice(s) such as device 110B. For example, user 130 can initiallyutilize device 110A (e.g., a smartphone device) and then later utilizedevice 110B (e.g., a desktop computer). Such a device 110B can includetask resumption service 113, which can be an application or module thatconfigures/enables device 110B to perform various operations such as aredescribed herein. For example, task resumption service 113 can configureor enable device 110B to receive previously registered/captured task(s)(e.g., a task registered at device 110A). Upon receiving such task(s),task resumption service 113 can resume the task, e.g., in conjunctionwith various application(s) 118 executing at device 11.0B, as describedin detail below.

Security engine 114 can configure/enable the device to ensure thesecurity of the task(s) captured/registered by task registration service112 and/or resumed by task resumption service 113. For example, it canbe appreciated that certain applications 118 (and/or content presentedwithin them) can be sensitive, confidential, private, etc. Accordingly,security engine 114 can operate in conjunction with task registrationservice 112/ task resumption service 113. In doing so, user 130 can, forexample, ‘opt-in,’ ‘opt-out,’ and/or otherwise configure varioussecurity parameters, settings, etc., with respect to the operation ofthe described technologies. For example, the user can configure whattypes of tasks should or should not be registered/resumed (e.g., don'tstore tasks for finance-related applications.). Additionally, securityengine 114 can utilize data encryption, identity verification, etc., toensure that the registered tasks cannot be accessed/retrieved byunauthorized parties. In doing so, security engine 114 can ensure thatthe described technologies enable the described benefits and technicalimprovements to be realized while maintaining the security and privacyof the user's data.

Additionally, in certain implementations security engine 116 can beconfigured to limit or prevent the registration and/or resumption ofvarious tasks that can compromise the security/stability of a device.For example, various system or operating system (OS)-level tasks canmalfunction or cause instability or damage if they are resumed atanother device. Accordingly, security engine 116 can be configured toidentify such tasks and to limit or prevent their registration and/orresumption. For example, in certain implementations security engine 116can be configured to only enable the resumption of a system or OS-leveltask at the same device at which such a task was captured. In otherimplementations, security engine 116 can be configured to only enablethe registration/resumption of tasks that do not effect system orOS-level functionality (and/or are otherwise determined not to causeetc., on the device at which they are being resumed).

Personal assistant engine 116 can configure/enable the device tointeract with, provide content to, and/or otherwise perform operationson behalf of user 130. For example, personal assistant engine 1.16 canreceive request(s) from user 130 and present/provide responses to suchrequest(s) (e.g., within a conversational or ‘chat’ interface). Incertain implementations, personal assistant engine 116 can also identifycontent that can be relevant to user 130 (e.g., based on a location ofthe user or other such context) and present such content to the user.Personal assistant engine 116 can also enable user 130 to initiateand/or configure various aspects of applications 118. For example, user130 can provide a command to personal assistant engine 116 (e.g., ‘playjazz music’). In response to such command, personal assistant engine 116can initiate an application 118 (e.g., a media player application).

Additionally, in certain implementations personal assistant engine 116can enable user 130 to manage various tasks 150. For example, as shownin FIG. 1, personal assistant engine 116 can execute on device 110A inconjunction with task registration service 112. In doing so, personalassistant engine 116 can, for example, prompt user 130 to provideinput/approval with respect to the registration of a task 150 withrespect to a particular application 118. Moreover, as also shown in FIG.1, personal assistant engine 116 can execute on device 110E inconjunction with task resumption service 113. In doing so, personalassistant engine 116 can, for example, notify user 130 of various storedtask(s) that can be resumed.

While device 110A is depicted as executing task registration service 112and/device 110B is depicted as executing task resumption service 113,such depiction is only for the sake of clarity. However, it should beunderstood that each of the depicted devices can include both taskregistration service 112 and task resumption service 113. Moreover, incertain implementations both task registration service 112 and taskresumption service 113 can execute concurrently on a single device 110.For example, task registration service 112 can register/capture a taskwith respect to one application 118A while task resumption service 113is resuming a task with respect to another application 118E on the samedevice. In an example, the task registration server 112 and taskresumption service can operate as a single service.

It should also be noted that while various components (e.g., taskregistration service 112, task resumption service 113, security engine114) are depicted (e.g., in FIG. 1) as operating on a device (e.g.,device 110A and/or device 110B), this is only for the sake of clarity.However, it should be understood that, in other implementations, thereferenced components (e.g., task registration service 112, taskresumption service 113, security engine 114) can also be implemented onother devices/machines. For example, in lieu of executing locally atdevice 110, task resumption service 113 can be implemented remotely,e.g., at server 140 (e.g., on a server device or within a cloud serviceor framework).

As also shown in FIG. 1, devices 110A and 110B can be connected toand/or otherwise communicate with server 140 via network 120. Network120 can include one or more networks such as the Internet, a wide areanetwork (WAN), a local area network (LAN), a virtual private network(VPN), an intranet, and the like. Server 140 can be, for example, aserver computer, computing device, storage service (e.g., a ‘cloud’service), etc., and can include task management engine 142, securityengine 114, and task store 160.

Task management engine 142 can be an application or module thatconfigures/enables server 140 to perform various operations such as aredescribed herein. For example, task management engine 142 can configureor enable server 140 to receive task(s) 150 (e.g., from device 110A),store such task(s) (e.g., in task store 160), and provide such task(s)(e.g., to device 110B) for resumption.

Task store 160 can be, for example, a database or repository that storesvarious information, such as task(s) 150 that are captured/registered atand/or otherwise provided by device(s) 110. FIG. I depicts an examplescenario in which task 150A and task 150B are stored in task store 160.As also shown in FIG. 1, task 150A can include elements such as anapplication identifier (‘application ID’) 152A, action 154A, entity156A, and state 158A. Other tasks 150 stored in task store 160 (e.g.,task 150B) can also include similar/comparable elements (e.g.,application ID 152B, action 154B, entity 156B, and state 158B, as shownin FIG. 1).

Application ID 152A can be, for example, an identifier (or any othersuch information or data element) that reflects or otherwise indicatesthe application(s) 118 with respect to which the task 150A pertains to.Such an application ID 152A can, for example, reflect or specify theparticular application 118A executing on device 110A with respect towhich the task 150A was registered (e.g., by task registration service112). Additionally, in certain implementations application ID 152A canreflect or indicate the type or class of application with respect towhich the task 150A was captured/registered. For example, application ID152A can reflect or specify that the task 150A was registered withrespect to a media player application, web browser application, etc.Various additional information or parameters can also be included. Forexample, application ID 152A can also reflect the particular version ofthe application that task 150A is captured with respect to. By way offurther example, application ID 152A can also reflect the operatingsystem (OS) within which the application (that task 150A is capturedwith respect to) is executing. Such information/parameters can befurther accounted for, e.g., in a scenario in which the task is to beresumed on a device having a different version of the application and/ora different OS, as described herein.

Action 154A can be, for example, be a parameter (or any other suchinformation or data element) that reflects or otherwise indicatesoperation(s), function(s), etc., being performed by the application(s)118 when the task 150A was registered/captured. For example, withrespect to a media player application, such an action 154A can be a‘play music’ operation performed by the application.

Entity 156A can be, for example, be a content item and/or a contentsource (or any other such information or data element) that reflects orotherwise indicates the content on which the application(s) 118 isperforming action 154A. For example, entity 156A can be a media file(e.g., an audio file that corresponds to a song) and/or the location ornetwork path of such a file that is being played by a media playerapplication.

State 158A can be, for example, be a status or progression (or any othersuch information or data element) that reflects or otherwise indicatesaspects of the manner in which the application(s) 118 have performedaction 154A with respect to entity 156A. For example, entity 158A canreflect the degree to which a ‘play music’ action has been performed bya media player application with respect to a particular song (e.g., 2minutes and 30 seconds of the song have been played).

As noted above, security engine 114 can configure/enable server 114 toensure the security of the task(s) 150 managed by task management engine142 and/or stored in task store 160. For example, security engine 114can utilize data encryption, identity verification, etc., to ensure thattasks 150 registered by a user 130 are only provided for resumption atanother device upon successful identity verification of the user 130 atsuch device.

While many of the examples described herein are illustrated with respectto a single server 140, this is simply for the sake of clarity andbrevity. However, it should be understood that the describedtechnologies can also be implemented (in any number of configurations)across multiple servers and/or other computing devices/services.

Further aspects and features of devices 110 and server 140 are describedin more detail in conjunction with FIGS. 2-6, below.

As used herein, the term “configured” encompasses its plain and ordinarymeaning. In one example, a machine is configured to carry out a methodby having software code for that method stored in a memory that isaccessible to the processor(s) of the machine. The processor(s) accessthe memory to implement the method. In another example, the instructionsfor carrying out the method are hard-wired into the processor(s). In yetanother example, a portion of the instructions are hard-wired, and aportion of the instructions are stored as software code in the memory.

FIG. 3 is a flow chart illustrating a method 300, according to anexample embodiment, for cross-device task registration and resumption.The method is performed by processing logic that can comprise hardware(circuitry, dedicated logic, etc.), software (such as is run on acomputing device such as those described herein), or a combination ofboth. In one implementation, the method 300 is performed by one or moreelements depicted and/or described in relation to FIG. 1 and/or FIG. 2(including but not limited to server 140), while in some otherimplementations, the one or more blocks of FIG. 3 can be performed byanother machine or machines.

For simplicity of explanation, methods are depicted and described as aseries of acts. However, acts in accordance with this disclosure canoccur in various orders and/or concurrently, and with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be required to implement the methods in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the methods could alternatively berepresented as a series of interrelated states via a state diagram orevents. Additionally, it should be appreciated that the methodsdisclosed in this specification are capable of being stored on anarticle of manufacture to facilitate transporting and transferring suchmethods to computing devices. The term article of manufacture, as usedherein, is intended to encompass a computer program accessible from anycomputer-readable device or storage media.

At operation 310, a first task is received. In certain implementations,such a task is received from a task registration service. Such a taskregistration service 112 can execute on a first device associated with auser 130 (e.g., device 110A as shown in FIG. 1). The referenced task 150can include various elements such as an application identifier 152. Suchan application identifier can identify an application 118 that executeson the device (e.g., the device 110 from which the task 150 isreceived). In certain implementations, various aspects of operation 310(as well as the other operations described with respect to FIG. 3) areperformed by server 140 and/or task management engine 142 (e.g., asdepicted in FIG. 1). In other implementations, such aspects can beperformed by one or more other elements/components, such as thosedescribed herein.

By way of illustration, FIG. 2 depicts an example scenario 200 in whichuser 130A utilizes device 210A (e.g. a smartphone). As shown in FIG. 2,task 250A is received from device 210A and stored in task store 260A ofserver 240. Task 250A can include application identifier 152A whichreflects that the task 250A was registered/captured (e.g. at device210A) with respect to a media player application.

As noted above, the referenced task(s) can include various additionalelements. For example, such task(s) can further include an action 154,such as an action associated with the application that executed on thefirst device (e.g., when the task was registered). By way of furtherillustration, such an action can be a parameter, data element, etc. thatreflects/indicates operation(s), function(s), etc., performed by anapplication when the task was registered/captured. For example, as shownin FIG. 2, action 154A is a ‘play music’ operation, reflecting that amedia player application was performing such an operation (e.g., atdevice 210A) when the task 250A was registered.

in certain implementations, the referenced task(s) can further include acontent item or entity 156. Such a content item/entity 156 can be acontent item, content source, etc. that reflects/indicates the contenton which the application(s) 118 is performing action 154A. For example,as shown in FIG. 2, content item/entity 156A can be a media file (e.g.,an audio file of ‘Song XYZ’) and/or the location or network path of sucha file that is being played by a media player application.

The referenced task(s) can also include state 158. The referenced statecan be, for example, an operation state associated with the application118 that executed on the device (e.g., when the task was registered).For example, the referenced state can be a status or progression thatreflects aspects of the manner in which application(s) 118 performedaction 154A with respect to entity 156A. For example, as shown in FIG.2, entity 158A reflects the status of the ‘play music’ action 154Aperformed by a media player application with respect to ‘Song XYZ’ 156A.Specifically, as shown in FIG. 2, state 158A reflects that 2 minutes and32 seconds (out of 4 minutes) of ‘Song XYZ’ have been played (e.g., atthe time the task 250A was registered at device 210A). By way of furtherexample, a state of another task can reflect that a user is currentlyreading page 11 (out of 26 pages) of a document. Accordingly, it shouldbe understood that the described technologies (e.g., in conjunction withthe described task registration and task resumption services) canregister/capture the state of a task with respect to practically anyapplication, and subsequently enable the resumption of such task (e.g.,at another device), as described herein.

Moreover, in certain implementations the referenced task is received inresponse to a user input. Such a user input can be provided to and/orreceived at a device (e.g., device 110A as shown in FIG. 1). Moreover,in certain implementations such an input is received with respect to anapplication (e.g., an application executing on the device). That is, itcan he appreciated that the described technologies can be configured tocapture/register various task(s) 150 in an automated fashion. Forexample, task registration service 112 can be configured toautomatically register a task associated with a particular application(e.g., a web browser) on a periodic/ongoing basis (e.g., every threeminutes). In contrast, the user can also configure task registrationservice 112 to capture/register task(s) associated with otherapplications in response to particular input(s). For example, taskregistration service 112 can be configured to register a task associatedwith a media player application when a specific input is providedreceived (e.g., ‘pause music’ input). In doing so, task registrationservice 112 can preserve processing resources, network bandwidth, etc.,by registering task(s) at intervals that the user is more likely to stopusing a certain device/application (e.g., when selecting ‘pause’).

At operation 320, a second task is received. In certain implementations,such a task 150 is received from another application that executes on adevice. For example, as shown in FIG. 1, task 150A is received fromdevice 110A with respect to application 118A and task 150B is receivedfrom device 110A with respect to application 118B.

At operation 330, a notification is received. In certainimplementations, such a notification can reflect that the user 130(e.g., the user with respect to which the tasks 150 captured atoperation(s) 310 and/or 320 were registered) has accessed a seconddevice. For example, as shown in FIG. 2, server 240 can receive anotification that user 130A (who had previously accessed device 210A)has now accessed device 210B. As noted above, such a notification caninclude and/or otherwise reflect various aspects of the verification ofthe identity of user 130A.

Moreover, in certain implementations the referenced notification caninclude and/or reflect a notification that the user has initiated anapplication (e.g., on the second device). For example, as shown in FIG.1, user 130 can utilize device 110A to execute application 118A, and atask 150A of such application is stored in task store 160. Subsequently,when utilizing device 110B, user 130 can initiate, launch, activate,etc., application 118A. Upon launching such application 118A, device110B transmits a notification which is received by server 140. Such anotification can reflect that the user has initiated the application118A (e.g., on the second device 110B).

Additionally, in certain implementations the referenced notification caninclude and/or reflect a request for a task (e.g., the task received atoperation 310). For example, in certain scenarios a user may not wish toresume some or all previously registered task(s) 150. Accordingly, incertain implementations the user can initially be presented with aprompt that provides the user with the option to request various task(s)150 from server 140. For example, user 130 can initially be presentedwith a graphical interface (e.g., via personal assistant engine 116)indicating that various task(s) 150 are stored and can be resumed on thedevice 110B. Upon receiving a selection of a particular task, anotification (which requests the selected task) is transmittedto/received by server 140. In doing so, computing resources, bandwidth,etc., can be preserved by providing the referenced task(s) 150 when theyare requested by the user 130.

At operation 340, a task (e.g., the task received at operation 310) isprovided to a second device (e.g., the device from which thenotification was received at operation 330). In certain implementationsthe task is provided to the task resumption service 113 of the device.Moreover, in certain implementations the task is provided in response toa notification (e.g., in response to receipt of the notification atoperation 330). For example, as shown in FIG. 2, user 130A (whopreviously utilized device 210A, e.g., a smartphone) can log on to orotherwise access device 210B (a desktop computer). Upon accessing device210B, a notification is transmitted by device 210B and received byserver 240. In response to such notification, task 250 (which had beenreceived from device 210A) is provided to device 210B. In doing so, user130A can resume the task at device 210B in an efficient and seamlessmanner.

Moreover, various instructions can also be incorporated within and/orprovided in conjunction with the referenced task 150 (e.g., the taskprovided to the second device utilized by the user 130). For example,the task can include/be accompanied by an instruction to install theapplication (e.g., the application to which the task pertains) at thesecond device. That is, it can be appreciated that a user can wish toresume a task 150 on a device upon which the associated application isnot installed. Accordingly, the task 150 provided to such a device caninclude an instruction to install the application 118 with respect towhich the task is associated. Such an instruction can, for example,include a link, location, etc., at which the application can bedownloaded or otherwise obtained. In doing so, the user can resume atask on a device upon which the associated application is not initiallyinstalled (e.g., by using the instruction to install the application andthen resuming the task).

It should be understood that, in certain implementations, multiple taskscan be provided to a device. For example, as shown in FIG. 1, task store160 can receive both task 150A and task 150B from device 110A. Task 150Acan be associated with application 118A (e.g., a media playerapplication) while task 150B is associated with application 118B (e.g.,a web browser). Upon receiving a notification from device 110B (e.g.,reflecting that user 130 has logged on to such a device), both task 150Aand task 150B can be provided to the device 110B. In doing so, the usercan resume multiple tasks (e.g., those associated with multipleapplications) at device 110B in an efficient/automated fashion.

Additionally, in certain implementations, in scenarios in which multipletasks (which can correspond to multiple applications) can be resumed,the manner in which such resumption is performed can be dictated basedon the ranking and/or prioritization of the referenced tasks. Forexample, in certain implementations, the referenced tasks can beassigned a weight or raking value which can reflect the significance orimportance associated with the resumption of such a task. Such a rankingcan be computed/dictated based on various factors such as the amount oftime a user is determined to spend using the application to which thetask corresponds. For example, the longer the user utilizes anapplication, the greater the importance/significance of task(s)registered with respect to such application. Other factors can also beaccounted for in determining/computing such a ranking. For example, incertain implementations the most recently captured tasks can beprovided/resumed first. In other implementations, the oldest capturedtasks can be provided/resumed first. It should also he noted thatmultiple factors (e.g., the amount of time a user spends in anapplication as well as how long ago the task was registered) can be usedto determine/compute the referenced ranking/prioritization value. Asnoted, such a ranking can dictate which task(s) are to beprovided/resumed first (e.g., in lieu of providing/resuming many storedtasks at the same time).

in certain implementations, a task can be provided in response to aspecific request for the task. For example, as noted above, in certainimplementations task(s) can be provided in an automated fashion (e.g.,when a user logs on to a second device). In other implementations, suchtask(s) can be provided in response to an affirmative request/selectionof the task. In such scenarios, personal assistant engine 116 can, forexample, initially present the user with option(s) to select task(s)stored at server 140 that can be resumed on device 110B. Upon receivinga selection of a particular task, a request can be transmittedto/received by server 140 and the requested task 150 can be provided inresponse.

Additionally, in certain implementations the referenced task(s) can beprovided (e.g., to device 110B) in a periodic, continuous, and/orongoing basis. For example, the described technologies can be configuredto maintain certain task(s) on multiple devices (e.g., devices 110A and110B). By way of illustration, in a scenario in which a user frequentlyswitches back and forth between devices (e.g., with respect toparticular task(s)), the described technologies can register suchtask(s) (e.g., at the device currently being used by the user) andresume them at the other device(s) on a continuous/ongoing basis.

It should also be noted that while many of the examples provided hereinpertain to the registration/capture of a task on one device and theresumption of the task at another device, the described technologies arenot so limited. For example, the described technologies can also beconfigured to capture/register a task at a device, and to subsequentlyresume the task at the same device. By way of illustration, thedescribed technologies can enable various task(s) from a device to beregistered and stored. The user may then turn off, log out of, etc., thedevice. Subsequently (e.g., when the user logs back onto the device),the described technologies can be used to resume the registered task(s)on the same device.

FIG. 4 is a flow chart illustrating a method 400, according to anexample embodiment, for cross-device task registration and resumption.The method is performed by processing logic that can comprise hardware(circuitry, dedicated logic, etc.), software (such as is run on acomputing device such as those described herein), or a combination ofboth. In one implementation, the method 400 is performed by one or moreelements depicted and/or described in relation to FIG. 1 and/or FIG.(including but not limited to device 110A), while in some otherimplementations, the one or more blocks of FIG. 4 can be performed byanother machine or machines.

At operation 410, an input is received. In certain implementations, suchan input is received at a first device (e.g., device 110A as depicted inFIG. 1). Moreover, in certain implementations such an input is receivedwith respect to a first application (e.g., application 118A as executingon device 110A). For example, such an input can correspond to aselection provided by user 130 (e.g., via personal assistant engine 116)indicating that a task associated with application 118A should beregistered. In certain implementations, various aspects of operation 410(as well as the other operations described with respect to FIG. 4) areperformed by device 110A and/or task registration service 112 (e.g., asdepicted in FIG. 1). In other implementations, such aspects can beperformed by one or more other elements/components, such as thosedescribed herein.

At operation 420, a first task 150 is registered. In certainimplementations, such a task is registered at device 110A. Such a device110A can be a device associated with a user 130 (e.g., a device that theuser has logged in to using his/her user account). As described indetail above, the referenced task that is registered/captured at device110A can include various elements (e.g., application identifier, action,content item/entity, and/or operation state, each of which is describedin detail above). For example, task registration service 112 can accessapplication 118A (and/or related processes or information on device 110Athat relate to the application). By accessing the application (and/orrelated processes or information), the various elements (action,operation state, etc.) can be identified and the task 150 can beregistered/captured by task registration service 112.

At operation 430, a second task can be registered. In certainimplementations, such a second task can be related to a secondapplication that is executing on the device (e.g., application 1188, asshown in FIG. 1).

At operation 440, the first task (e.g., as registered at operation 420)and/or the second task (e.g., as registered at operation 430) isprovided or otherwise transmitted. In certain implementations, suchtasks are transmitted to a task management service (e.g., taskmanagement engine 142 as executing on server 140).

FIG. 5 is a flow chart illustrating a method 500, according to anexample embodiment, for cross-device task registration and resumption.The method is performed by processing logic that can comprise hardware(circuitry, dedicated logic, etc.), software (such as is run on acomputing device such as those described herein), or a combination ofboth. In one implementation, the method 500 is performed by one or moreelements depicted and/or described in relation to FIG. 1 and/or FIG. 2(including but not limited to device 110B), while in some otherimplementations, the one or more blocks of FIG. 5 can be performed byanother machine or machines.

At operation 510, a notification is provided. In certainimplementations, such a notification is provided to a task managementservice (e.g., task management engine 142 of server 140). Such anotification can, for example, reflect or otherwise indicate that aparticular user has accessed a particular device (e.g., logged on to thedevice with his/her user account). For example, when user 130 logs on todevice 110E (as shown in FIG. 1), task resumption service 113 cantransmit a notification (reflecting such a log on) to server 140/taskmanagement engine 142. Moreover, in certain implementations such anotification can reflect that such a user has initiated, launched, etc.a particular application 118 on the device. In certain implementations,various aspects of operation 510 (as well as the other operationsdescribed with respect to FIG. 5) can be performed by device 110B and/ortask resumption service 113 (e.g., as depicted in FIG. 1). In otherimplementations such aspects can be performed by one or more otherelements/components, such as those described herein.

At operation 520, a first task is received (e.g., at the device thatprovided the notification at operation 510, such as device 110B as shownin FIG. 1). Such a first task can include various elements (e.g.,application identifier, action, content item/entity, and/or operationstate, each of which is described in detail above). It should beunderstood that the referenced task can originate from device 110A(which the user 130 was previously utilizing). The task can reflectvarious aspects of the execution of an application 118 at such a device110A. Such a task is stored at task store 160 of server 140, andprovided to/received by device 110B (e.g., in response to thenotification provided at operation 510). As noted above, in certainimplementations such a task can be received in response to thereferenced notification. Additionally, in other implementations such atask(s) can be provided to/received by the device in a periodic,continuous, and/or ongoing basis. For example, as described above, incertain scenarios a task can be registered at one device and resumed atanother device on an ongoing basis (e.g., to enable the user toseamlessly switch between devices).

At operation 530, a selection can be received (e.g., at device 110B asshown in FIG. 1). In certain implementations, such a selection can be aselection of a task as stored in task store 160 of server 140. Forexample, personal assistant engine 116 can present a graphical interfaceat device 110B that reflects various stored task(s) 150 that can beresumed on the device 110B. User 130 can then select one or more of thepresented task(s). In doing so, the selected task can be requested fromserver 140.

At operation 540, a task can be resumed, e.g., device 110B. In certainimplementations, such a task can be resumed in response to a selection(e.g., the selection received at operation 530). In doing so, taskresumption service 113 can utilize task 150 to initialize thecorresponding application (e.g., application 118A as executing on device110B). For example, the action, entity, etc. information included in thetask 150 can be used to configure application 118A on device 110B in amanner that reflects the execution of the application on device 110A(e.g., when the task was registered).

Moreover, as noted above, in certain implementations resuming a firsttask at a device (e.g., device 110B) can include installing anapplication 118 at the device. For example, task 150 can include and/orbe accompanied by an instruction, link, location, etc., at which theapplication can be downloaded or otherwise obtained. Utilizing such aninstruction, link, etc., task resumption service 113 can configuredevice 110E to install the corresponding application 118 (and thenresume the task using the installed application).

Additionally, as noted above, various aspects of the application(s) atwhich a task is registered/resumed (and/or the operating system(s) onwhich such application(s) execute) can be accounted for in resuming thetask. For example, the version of the application (and/or the OS) withrespect to which a task was captured and/or the version of theapplication (and/or the OS) with respect to which a task is beingresumed can be accounted for when resuming the task. In doing so,various aspects of the task can be updated (e.g., with respect todifferences between the respective versions of the application,operating systems). In doing so, tasks captured in one context (e.g.,with respect to a certain application version/OS) can be resumed withinanother context (e.g., with respect to a certain applicationversion/OS).

It should also be noted that while the technologies described herein areillustrated primarily with respect to the registration and resumption oftasks, the described technologies can also be implemented in any numberof additional or alternative settings or contexts and towards any numberof additional objectives. It should be understood that further technicaladvantages, solutions, and/or improvements (beyond those describedand/or referenced herein) can be enabled as a result of suchimplementations.

Certain implementations are described herein as including logic or anumber of components, modules, or mechanisms. Modules can constituteeither software modules (e.g., code embodied on a machine-readablemedium) or hardware modules. A “hardware module” is a tangible unitcapable of performing certain operations and can be configured orarranged in a certain physical manner. In various exampleimplementations, one or more computer systems (e.g., a standalonecomputer system, a client computer system, or a server computer system)or one or more hardware modules of a computer system (e.g., a processoror a group of processors) can be configured by software (e.g., anapplication or application portion) as a hardware module that operatesto perform certain operations as described herein.

In some implementations, a hardware module can he implementedmechanically, electronically, or any suitable combination thereof. Forexample, a hardware module can include dedicated circuitry or logic thatis permanently configured to perform certain operations. For example, ahardware module can be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated. Circuit (ASIC). A hardware module can also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardware modulecan include software executed by a general-purpose processor or otherprogrammable processor. Once configured by such software, hardwaremodules become specific machines (or specific components of a machine)uniquely tailored to perform the configured functions and are no longergeneral-purpose processors. It will be appreciated that the decision toimplement a hardware module mechanically, in dedicated and permanentlyconfigured circuitry, or in temporarily configured circuitry (e.g.,configured by software) can be driven by cost and time considerations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringimplementations in which hardware modules are temporarily configured(e.g., programmed), each of the hardware modules need not be configuredor instantiated at any one instance in time. For example, where ahardware module comprises a general-purpose processor configured bysoftware to become a special-purpose processor, the general-purposeprocessor can be configured as respectively different special-purposeprocessors (e.g., comprising different hardware modules) at differenttimes. Software accordingly configures a particular processor orprocessors, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules can be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications can be achievedthrough signal transmission (e.g., over appropriate circuits arid buses)between or among two or more of the hardware modules. In implementationsin which multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules can beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module can perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module can then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules can also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein can beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors can constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein can be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method can be performed by one or more processors orprocessor-implemented modules. Moreover, the one or more processors canalso operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations can be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an API).

The performance of certain of the operations can be distributed amongthe processors, not only residing within a single machine, but deployedacross a number of machines. In some example implementations, theprocessors or processor-implemented modules can be located in a singlegeographic location (e.g., within a home environment, an officeenvironment, or a server farm). In other example implementations, theprocessors or processor-implemented modules can be distributed across anumber of geographic locations.

The modules, methods, applications, and so forth described inconjunction with FIGS. 1-5 are implemented in some implementations inthe context of a machine and an associated software architecture. Thesections below describe representative software architecture(s) andmachine (e.g., hardware) architecture(s) that are suitable for use withthe disclosed implementations.

Software architectures are used in conjunction with hardwarearchitectures to create devices and machines tailored to particularpurposes. For example, a particular hardware architecture coupled with aparticular software architecture will create a mobile device, such as amobile phone, tablet device, or so forth. A slightly different hardwareand software architecture can yield a smart device for use in the“internet of things,” while yet another combination produces a servercomputer for use within a cloud computing architecture. Not allcombinations of such software and hardware architectures are presentedhere, as those of skill in the art can readily understand how toimplement the inventive subject matter in different contexts from thedisclosure contained herein.

FIG. 6 is a block diagram illustrating components of a machine 600,according to some example implementations, able to read instructionsfrom a machine-readable medium (e.g., a machine-readable storage medium)and perform any one or more of the methodologies discussed herein.Specifically, FIG. 6 shows a diagrammatic representation of the machine600 in the example form of a computer system, within which instructions616 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 600 to perform any one ormore of the methodologies discussed herein can be executed. Theinstructions 616 transform the general, non-programmed machine into aparticular machine programmed to carry out the described and illustratedfunctions in the manner described. In alternative implementations, themachine 600 operates as a standalone device or can be coupled (e.g.,networked) to other machines. In a networked deployment, the machine 600can operate in the capacity of a server machine or a client machine in aserver-client network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine 600 cancomprise, but not be limited to, a server computer, a client computer,PC, a tablet computer, a laptop computer, a netbook, a set-top box(STB), a personal digital assistant (PDA), an entertainment mediasystem, a cellular telephone, a smart phone, a mobile device, a wearabledevice (e.g., a smart watch), a smart home device (e.g., a smartappliance), other smart devices, a web appliance, a network router, anetwork switch, a network bridge, or any machine capable of executingthe instructions 616, sequentially or otherwise, that specify actions tobe taken by the machine 600. Further, while only a single machine 600 isillustrated, the term “machine” shall also be taken to include acollection of machines 600 that individually or jointly execute theinstructions 616 to perform any one or more of the methodologiesdiscussed herein.

The machine 600 can include processors 610, memory/storage 630, and I/Ocomponents 650, which can be configured to communicate with each othersuch as via a bus 602. In an example implementation, the processors 610(e.g., a Central Processing Unit (CPU), a Reduced. Instruction SetComputing (RISC) processor, a Complex Instruction Set Computing (CNC)processor, a Graphics Processing Unit (CPU), a Digital Signal Processor(DSP), an ASIC, a Radio-Frequency Integrated Circuit (RFIC), anotherprocessor, or any suitable combination thereof) can include, forexample, a processor 612 and a processor 614 that can execute theinstructions 616. The term “processor” is intended to include multi-coreprocessors that can comprise two or more independent processors(sometimes referred to as “cores”) that can execute instructionscontemporaneously. Although FIG. 6 shows multiple processors 610, themachine 600 can include a single processor with a single core, a singleprocessor with multiple cores (e.g., a multi-core processor), multipleprocessors with a single core, multiple processors with multiples cores,or any combination thereof.

The memory/storage 630 can include a memory 632, such as a main memory,or other memory storage, and a storage unit 636, both accessible to theprocessors 610 such as via the bus 602. The storage unit 636 and memory632 store the instructions 616 embodying any one or more of themethodologies or functions described herein. The instructions 616 canalso reside, completely or partially, within the memory 632, within thestorage unit 636, within at least one of the processors 610 (e.g.,within the processor's cache memory), or any suitable combinationthereof, during execution thereof by the machine 600. Accordingly, thememory 632, the storage unit 636, and the memory of the processors 610are examples of machine-readable media.

As used herein, “machine-readable medium” means a device able to storeinstructions (e.g., instructions 616) and data temporarily orpermanently and can include, but is not limited to, random-access memory(RAM), read-only memory (ROM), buffer memory, flash memory, opticalmedia, magnetic media, cache memory, other types of storage (e.g.,Erasable Programmable Read-Only Memory (EEPROM)), and/or any suitablecombination thereof. The term “machine-readable medium” should be takento include a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storethe instructions 616. The term “machine-readable medium” shall also betaken to include any medium, or combination of multiple media, that iscapable of storing instructions (e.g., instructions 616) for executionby a machine (e.g., machine 600), such that the instructions, whenexecuted by one or more processors of the machine (e.g., processors610), cause the machine to perform any one or more of the methodologiesdescribed herein. Accordingly, a “machine-readable medium” refers to asingle storage apparatus or device, as well as “cloud-based” storagesystems or storage networks that include multiple storage apparatus ordevices. The term “machine-readable medium” excludes signals per se.

The I/O components 650 can include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 650 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones will likely include a touch input device or other such inputmechanisms, while a headless server machine will likely not include sucha touch input device. It will be appreciated that the I/O components 650can include many other components that are not shown in FIG. 6. The I/Ocomponents 650 are grouped according to functionality merely forsimplifying the following discussion and the grouping is in no waylimiting. In various example implementations, the I/O components 650 caninclude output components 652 and input components 654. The outputcomponents 652 can include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 654 can include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or another pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example implementations, the I/O components 650 can includebiometric components 656, motion components 658, environmentalcomponents 660, or position components 662, among a wide array of othercomponents. For example, the biometric components 656 can includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 658 can includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 660 can include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detect concentrations of hazardous gases for safetyor to measure pollutants in the atmosphere), or other components thatcan provide indications, measurements, or signals corresponding to asurrounding physical environment. The position components 662 caninclude location sensor components (e.g., a Global Position System (GPS)receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude can be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication can be implemented using a wide variety of technologies.The I/O components 650 can include communication components 664 operableto couple the machine 600 to a network 680 or devices 670 via a coupling682 and a coupling 672, respectively. For example, the communicationcomponents 664 can include a network interface component or othersuitable device to interface with the network 680. In further examples,the communication components 664 can include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 670 can be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 664 can detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 664 can include Radio Frequency Identification(REID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information can be derived via the communication components664, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that can indicate a particular location, and so forth.

In various example implementations, one or more portions of the network680 can be an ad hoc network, an intranet, an extranet, a virtualprivate network (VPN), a local area network (LAN), a wireless LAN(WLAN), a WAN, a wireless WAN (WWAN), a metropolitan area network (MAN),the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, the network 680 or a portion of the network 680can include a wireless or cellular network and the coupling 682 can be aCode Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or another type of cellular orwireless coupling. In this example, the coupling 682 can implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1xRTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,

Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LIE) standard, othersdefined by various standard-setting organizations, other long rangeprotocols, or other data transfer technology.

The instructions 616 can be transmitted or received over the network 680using a transmission medium via a network interface device (e.g., anetwork interface component included in the communication components664) and utilizing any one of a number of well-known transfer protocols(e.g., HTTP). Similarly, the instructions 616 can be transmitted orreceived using a transmission medium via the coupling 672 (e.g., apeer-to-peer coupling) to the devices 670. The term “transmissionmedium” shall be taken to include any intangible medium that is capableof storing, encoding, or carrying the instructions 616 for execution bythe machine 600, and includes digital or analog communications signalsor other intangible media to facilitate communication of such software.

Throughout this specification, plural instances can implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations can be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationscan be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component can beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example implementations, variousmodifications and changes can be made to these implementations withoutdeparting from the broader scope of implementations of the presentdisclosure. Such implementations of the inventive subject matter can bereferred to herein, individually or collectively, by the term“invention” merely for convenience and without intending to voluntarilylimit the scope of this application to any single disclosure orinventive concept if more than one is, in fact, disclosed.

The implementations illustrated herein are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed. Other implementations can be used and derived therefrom, suchthat structural and logical substitutions and changes can be madewithout departing from the scope of this disclosure. The DetailedDescription, therefore, is not to be taken in a limiting sense, and thescope of various implementations is defined only by the appended claims,along with the full range of equivalents to which such claims areentitled.

As used herein, the term “or” can be construed in either an inclusive orexclusive sense. Moreover, plural instances can be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and can fall within a scope of various implementations of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations can be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource can be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of implementations ofthe present disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to he regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A system comprising: a processing device; and amemory coupled to the processing device and storing instructions that,when executed by the processing device, cause the system to performoperations comprising: receiving, from a task registration service of afirst device associated with a user, a first task, the first taskcomprising a first application identifier that identifies a firstapplication as executed on the first device; receiving a notification athe user as accessed a second device; and in response to thenotification, providing the first task to a task resumption service ofthe second device.
 2. The system of claim 1, wherein the first taskfurther comprises an action associated with the first application asexecuted on the first device.
 3. The system of claim 1, wherein thefirst task further comprises a content item associated with the firstapplication as executed on the first device.
 4. The system of claim 1,wherein the first task further comprises an operation state associatedwith the first application as executed on the first device.
 5. Thesystem of claim 1, wherein receiving the first task comprises receivingthe first task in response to a user input received at the first devicewith respect to the first application.
 6. The system of claim 1, whereinthe notification comprises a notification that the user has initiatedthe first application on the second device.
 7. The system of claim 1,wherein providing the first task further comprises providing aninstruction to install the first application at the second device. 8.The system of claim 1, wherein the memory further stores instructionsfor causing the system to perform operations comprising receiving asecond task from a second application that executes on the first device.9. The system of claim 8, wherein providing the first task comprisesproviding the first task and the second task to the task resumptionservice of the second device.
 10. The system of claim 1, whereinreceiving a notification that the user has accessed the second devicecomprises receiving, from the second device, a request for the firsttask.
 11. The system of claim 10, wherein providing the first taskcomprises providing the first task to the task resumption service inresponse to the request.
 12. A method comprising: registering, at afirst device associated with a user, a first task, the first taskcomprising: a first application identifier that identifies a firstapplication that executes on the first device, an action associated withthe first application as executed on the first device, a content itemassociated with the first application as executed on the first device,and an operation state associated with the first application as executedon the first device; and providing the first task to a task managementservice.
 13. The method of claim 12, further comprising receiving aninput from the user at the first device with respect to the firstapplication.
 14. The method of claim 13, wherein registering the firsttask comprises registering the first task in response to receiving theinput.
 15. The method of claim 12, further comprising registering asecond task, the second task being related to a second applicationexecuting on the first device.
 16. A non-transitory computer readablemedium having instructions stored thereon that, when executed by aprocessing device, cause the processing device to perform operationscomprising: receiving, at a first device associated with a user, a firsttask, the first task comprising: a first application identifier thatidentifies a first application that executed on a second deviceassociated with the user, an action associated with the firstapplication as executed on the second device, a content item associatedwith the first application as executed on the second device, and anoperation state associated with the first application as executed on thesecond device: and resuming the first task at the first device.
 17. Thecomputer-readable medium of claim 16, wherein the medium further storesinstructions for causing the processing device to perform operationscomprising providing a notification to a task management service thatthe user has accessed the first device.
 18. The computer-readable mediumof claim 16, wherein the medium further stores instructions for causingthe processing device to perform operations comprising providing anotification to a task management service that the user has initiatedthe first application on the first device.
 19. The computer-readablemedium of claim 16, wherein the medium further stores instructions forcausing the processing device to perform operations comprising receivinga selection of the first task at the first device, wherein resuming thefirst task comprises resuming the first task at the first device inresponse to the selection.
 20. The computer-readable medium of claim 16,wherein resuming the first task at the first device comprises:installing the first application at the first device; and resuming thefirst task with respect to the first application as installed on thefirst device.